fixed the documentation on the doc

@fospring @ailisp I think it would be much clearer if we follow this idea: https://github.com/nameskyteam/borsher

Basically, it would look like this:

import {Schema} from 'near-sdk-js'

class Car {
  schema = { brand: Schema.string, velocity: Schema.number }
}

class Contract {
  schema = {
    field1: Schema.string,
    field2: Schema.HashMap(Schema.string, Schema.number),
    field3: Schema.Array(Schema.bigInt),
    field4: Schema.Class(Car)
    field5: Schema.Option(number)
  }
}

This has several advantages:

• The Schema object makes the schema error-proof.
• All fields are always well defined, making it easy to (de)serialize them
• It can be used across JSON and Borsh serialization.

We could even just grab the https://github.com/nameskyteam/borsher and import it directly into here.

@fospring @ailisp I think it would be much clearer if we follow this idea: https://github.com/nameskyteam/borsher

Basically, it would look like this:

import {Schema} from 'near-sdk-js'

class Car {
  schema = { brand: Schema.string, velocity: Schema.number }
}

class Contract {
  schema = {
    field1: Schema.string,
    field2: Schema.HashMap(Schema.string, Schema.number),
    field3: Schema.Array(Schema.bigInt),
    field4: Schema.Class(Car)
    field5: Schema.Option(number)
  }
}

This has several advantages:

• The Schema object makes the schema error-proof.
• All fields are always well defined, making it easy to (de)serialize them
• It can be used across JSON and Borsh serialization.

We could even just grab the https://github.com/nameskyteam/borsher and import it directly into here.

great suggestion! I will update it

@gagdiez great suggestion! If it's adding a lot work, let's keep the behavior for:

• collections, maybe look like: Schema.Class(LookupMap, <schema of the value>)
• for primitive types like field1: Schema.string, it can be omitted from schema

@gagdiez great suggestion! If it's adding a lot work, let's keep the behavior for:

• collections, maybe look like: Schema.Class(LookupMap, <schema of the value>)
• for primitive types like field1: Schema.string, it can be omitted from schema

It looks a little difficult, I will try to resolve it in a new MR

@fospring sounds good to me, ping me and I'll see to help as well

@fospring sounds good to me, ping me and I'll see to help as well

Great!